Allow for insecure https connections to upstream MCP servers w/ --insecure flag #132
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jessesanford
force-pushed
the
allow-insecure-tls-with-override
branch
2 times, most recently
from
acbb2a4 to
d39a31e
Compare
Signed-off-by: Jesse Sanford <[email protected]>
jessesanford
force-pushed
the
allow-insecure-tls-with-override
branch
from
c3bb896 to
1f4bebf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many times when developing an MCP server we will want to test https or do integration testing with self-signed certificates. We should allow for this, just like curl and other common http libs/utils do, but with the caveat that it is not default. This PR allows for a --insecure flag to be passed which will enable the acceptance of such insecure connections.